• [ENH] Optimize FTS #5592 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

Optimize FTS by Replacing get_range with get_prefix in Full Text Search

This pull request improves the Full Text Search (FTS) functionality in the rust/index/src/fulltext/types.rs module by replacing usages of the get_range method with the more efficient get_prefix method for blockfile reads. This change is scoped to several call sites within token/posting list lookup and affects the retrieval and processing logic in both the main FTS search and associated utility/test functions. Minor additional corrections are made to tuple field unpacking and mapping, aligning the data access pattern with the slightly changed result shape from get_prefix.

This summary was automatically generated by @propel-code-bot